AUTHORS: Jonas P. Da Silva, Jair M. Abe, Luiz A. De Lima, Felipe S. David De Oliveira, Kazumi Nakamatsu
Download as PDF
ABSTRACT: Information Technology (IT) projects have been highlighted in the organizational environment since the results of these projects impact in organizations’ strategy. Good practices of project managements defend high-quality projects to deliver it within scope, on time, and within budget. In this sense, to deliver a project on time and a budget, it is necessary that their scope be well defined. However, the project team is faced with difficulties in understanding business requirements. Consequently, it causes project failures and affects the user’s satisfaction. Project software metrics as Function Points (FP) is taking a growing interest in the organization to control the scope of IT projects. Despite the importance of this theme, there are few empirical studies on the practical use of these metrics to IT Projects Scope Control (ITPSC). Considering this gap, the objective of this research is twofold: 1. identify the use of software metrics to ITPSC, and 2. provide a proposal of software metrics use based on FP to ITPSC. This is an exploratory qualitative study based on literature review and paracon-sistent logic. The literature review is based on academic papers published in the last 10 years. This paper contributes to academy area by offering an overview of how software metrics are being used by organizations to control the ITPSC and present a proposal of how they can be used to control the ITPSC
KEYWORDS: - Software Metrics; Scope Control; IT Project; Paraconsistent Logic.
REFERENCES:
[1] ABE, J. M., AKAMA, S., & NAKAMATSU, K. (2015). Introduction to Annotated Logics - Foundations for Paracomplete and Paraconsistent Reasoning. Springer.Author, Title of the Book, Publishing House, 200X.
[2] ASH, C. (2007). Convergence of its project management and change management: a comparative study. CEPIS promotes 47.
[3] BOWER, D. (2007). Earned Value Survey. New Directions in Project Performance and Progress Evaluation, 233.
[4] FRIMPON, M. F. (2012). A project approach to enterprise resource planning implementation. International journal of business and management, 7(10), 116-133.
[5] GÖRÖG, M. (2016). A broader approach to organizational project management maturity assessment. International Journal of Project Management, 34(8), 1658-1669.
[6] HEMINGWAY, C. J., & PEPPARD, J. (2007). Information Design: A Project Paradigm for Realizing Business Value from Information Technology. Communications of the ACM.
[7] IFPUG (2010: Function Point Counting Practices Manual, v4.3.1. Disponível em https://www.ifpug.org ISO 20926, 2009.
[8] KERZNER, H. (2011). Project Management Metrics, KPIs, and Dashboards. Hoboken, NJ: John Wiley & Sons, Inc.
[9] KUTSCH, E., WARD, J., HALL, M., & ALGAR, J. (2015). The contribution of the project management office: A balanced scorecard perspective. Information Systems Management, 32(2), 105-118.
[10] LEE, J. H., SHIM, H. J., & KIM, K. K. (2010). Critical success factors in SOA implementation: an exploratory study. Information Systems Management, 27(2), 123-145.
[11] LEVINSON, M. (2008, July 23). Project Management: The 14 Most Common Mistakes IT Departments Make. Retrieved July 5, 2011, from CIO Magazine: https://www.cio.com/article/438930
[12] LEVINSON, M. (2009, June 18). Recession Causes Rising I.T. Project Failure Rates. Retrieved July 5, 2011, from CIO Magazine: https://www.cio.com/article/495306
[13] MCQUIGHAN, J. M. (2013). A fuzzy computational intelligence approach to monitoring information technology project scope. Towson University Institutional Repository.
[14] NECHAEVA, I. (2016). BUILDING INFORMATION MODELLING (BIM) IN CONSTRUCTION PROJECT MANAGEMENT RUSSIA. Project Management Development–Practice and Perspectives, 213.
[15] PATTON, M. Q. (2015). Qualitative research & evaluation methods (4th ed.). Thousand Oaks, California: SAGE Publications Inc.
[16] PMI. (2013). A Guide to the Project Management Body of Knowledge: PMBOK Guide (5o ed). Project Management Institute, Incorporated.
[17] RICHARDSON, G., & BUTLER, C. (2006). Readings in Information Technology Project Management. Boston, MA: Course Technology Thomson Learning.
[18] ROWE, FRANTZ (2014). What literature review is not: diversity, boundaries, and recommendations. EJIS 23(3): 241-255.
[19] ULLAH, A., & LAI, R. (2011). A Requirements Engineering Approach to Improving Ibusiness Alignment. In J. Pokorny, V. Repa, K. Richta, W. Wojtkowski, H. Linger, C.
[20] WESTLAND, J. (2007). The Project Management Life Cycle: A Complete Step-ByStep Methodology for Initiating, Planning, Executing & Closing a Project Successful. Kogan Page Publishers.
